home *** CD-ROM | disk | FTP | other *** search
-
-
-
- RRRRTTTTMMMMOOOONNNN----CCCCLLLLIIIIEEEENNNNTTTT((((1111)))) RRRRTTTTMMMMOOOONNNN----CCCCLLLLIIIIEEEENNNNTTTT((((1111))))
-
-
-
- NNNNAAAAMMMMEEEE
- rtmon-client - client for collecting real-time event data from rtmond
-
- SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
- rrrrttttmmmmoooonnnn----cccclllliiiieeeennnntttt [ ----dddd ] [ ----ffff _f_i_l_e_n_a_m_e ] [ ----hhhh _h_o_s_t_n_a_m_e ] [ ----pppp _c_p_u-_l_i_s_t ] [ ----mmmm
- _e_v_e_n_t-_m_a_s_k ] [ ----nnnn ] [ ----OOOO ] [ ----tttt _t_i_m_e_o_u_t ] [ ----vvvv ]
-
- DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
- rrrrttttmmmmoooonnnn----cccclllliiiieeeennnntttt connects to the rrrrttttmmmmoooonnnndddd daemon running on the machine
- _h_o_s_t_n_a_m_e and collects event data for one or more CPUs. This event data
- can be displayed by programs such as ppppaaaarrrr(1), rrrrttttmmmmoooonnnn----dddduuuummmmpppp(1), and the
- optional IIIIRRRRIIIIXXXXvvvviiiieeeewwww(1) product.
-
- If event collection is done for an unspecified period of time (see the ----tttt
- option below) then rrrrttttmmmmoooonnnn----cccclllliiiieeeennnntttt will collect event data until it is
- interrupted.
-
- OOOOPPPPTTTTIIIIOOOONNNNSSSS
- ----dddd Enable debugging. Debugging enables additional error messages and
- the creation of a debugging file that contains a human readable list
- of the events that were collected (see the ----ffff option below).
-
- ----ffff _f_i_l_e_n_a_m_e
- Write event data to one or more files with names derived from
- _f_i_l_e_n_a_m_e. In normal operation rrrrttttmmmmoooonnnn----cccclllliiiieeeennnntttt will write all event
- data to a single file named _f_i_l_e_n_a_m_e. If the ----OOOO option is specified
- then event data is written to multiple files, one for each CPU where
- data is collected, and these files are named _f_i_l_e_n_a_m_e.wwwwvvvvrrrr._c_p_u, where
- _c_p_u is the number of the CPU on which data was collected. In
- addition, if debugging is enabled with the ----dddd option, per-CPU
- debugging information is written to files named _f_i_l_e_n_a_m_e.ddddbbbbgggg._c_p_u.
- By default rrrrttttmmmmoooonnnn----cccclllliiiieeeennnntttt uses the string ddddeeeeffffaaaauuuulllltttt in constructing file
- names.
-
- ----hhhh hhhhoooossssttttnnnnaaaammmmeeee
- Connect to the server on the specified host. rrrrttttmmmmoooonnnn----cccclllliiiieeeennnntttt first
- tries to use _h_o_s_t_n_a_m_e as the pathname of a UNIX domain socket on the
- local host; that failing it tries it as a host name or Internet
- address (specified using the usual ``dot notation''). If _h_o_s_t_n_a_m_e
- is an empty string then rrrrttttmmmmoooonnnn----cccclllliiiieeeennnntttt uses the default scheme for
- connecting to a server: first try to reach a server through the
- default UNIX domain socket, if that fails contact a server through
- the loopback interface.
-
- ----pppp _c_p_u-_l_i_s_t
- Collect data on the set of CPUs specified by _c_p_u-_l_i_s_t. CPUs are
- specified as a comma-separated list of CPU numbers or range of CPU
- numbers. CPUs are numbered starting at zero. For example, ----pppp _1,_4-
- _7,_1_1 means processors 1, 4, 5, 6, 7, and 11. An open-ended range is
- interpreted as all CPUs to the maximum CPU number; e.g. _2- on an
- 8-processor system is the same as _2-_7. The CPU list must be one
- string with no white space. By default, rrrrttttmmmmoooonnnn----cccclllliiiieeeennnntttt collects data
-
-
-
- PPPPaaaaggggeeee 1111
-
-
-
-
-
-
- RRRRTTTTMMMMOOOONNNN----CCCCLLLLIIIIEEEENNNNTTTT((((1111)))) RRRRTTTTMMMMOOOONNNN----CCCCLLLLIIIIEEEENNNNTTTT((((1111))))
-
-
-
- for all CPUs.
-
- ----mmmm _e_v_e_n_t-_m_a_s_k
- Collect only events specified by _e_v_e_n_t-_m_a_s_k. An _e_v_e_n_t _m_a_s_k
- specifies a set of events; it is a set of _e_v_e_n_t _c_l_a_s_s_e_s with each
- class specified symbolically as one of the following:
-
- NNNNaaaammmmeeee DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn
- all All events (default)
- alloc Memory allocation
- disk Disk i/o work
- intr Hardware interrupts
- io I/O-related events (disk+intr)
- netflow Network I/O flow
- netsched Network I/O scheduling
- network Network-related events (netflow+netsched)
- profile Kernel profiling
- scheduler Process and thread scheduler
- signal Signal delivery and reception
- syscall System calls and their arguments
- task Process and thread scheduling
- taskproc Process scheduling (system threads are not included)
- vm Virtual memory operation
-
- Event class names are case insensitive; i.e. ``SIGNAL'' is
- interpreted the same as ``signal''. Multiple event classes may be
- included by using a ``+'', ``|'', or ``,'' symbol to separate the
- names. Event classes may be excluded by using a ``-'' to separate
- the name. For example, ``network+io-disk'' indicates all network
- and i/o events should be included except for disk-related events.
- In addition to the above names, a number may be used to specify a
- value, where the various events are selected by bits in the value,
- as defined in ``<sys/rtmon.h>''.
-
- Note that under some circumstances events not in the specified
- classes may also be collected. This can happen when ``unclassified
- events'', such as those generated by user applications, are
- collected.
-
- ----nnnn Do not merge the per-CPU event data streams. This can be useful if
- merging slows down rrrrttttmmmmoooonnnn----cccclllliiiieeeennnntttt so much that it causes data to
- dropped by the server.
-
- ----tttt _t_i_m_e_o_u_t
- Collect data for _t_i_m_e_o_u_t seconds.
-
- ----vvvv When rrrrttttmmmmoooonnnn----cccclllliiiieeeennnntttt is used to collect data from a remote system (via
- the ----hhhh option) it is not normally possible to collect system call
- event data for processes unless the remote processes are specially
- marked to allow the data to be collected. This marking must be
- performed on the remote system via rrrrttttmmmmoooonnnn----rrrruuuunnnn(1). Permissions to
- perform this marking are handled via standard process permissions on
-
-
-
- PPPPaaaaggggeeee 2222
-
-
-
-
-
-
- RRRRTTTTMMMMOOOONNNN----CCCCLLLLIIIIEEEENNNNTTTT((((1111)))) RRRRTTTTMMMMOOOONNNN----CCCCLLLLIIIIEEEENNNNTTTT((((1111))))
-
-
-
- the remote system. Access to the system call data is controlled via
- a security cookie that is granted by the remote rrrrttttmmmmoooonnnndddd. When the ----vvvv
- option is provided to rrrrttttmmmmoooonnnn----cccclllliiiieeeennnntttt this security cookie is printed.
- The security cookie must then be used in the rrrrttttmmmmoooonnnn----rrrruuuunnnn command on
- the remote system in order to properly tag the collected system call
- data.
-
- DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
- _U_n_a_b_l_e _t_o _c_o_n_t_a_c_t _r_t_m_o_n _s_e_r_v_i_c_e _o_n _h_o_s_t <_h_o_s_t_n_a_m_e>. There is no rrrrttttmmmmoooonnnndddd
- server process running on the target system.
-
- SSSSEEEEEEEE AAAALLLLSSSSOOOO
- ppppaaaarrrr(1), rrrrttttmmmmoooonnnn----rrrruuuunnnn(1), rrrrttttmmmmoooonnnndddd(1), IIIIRRRRIIIIXXXXvvvviiiieeeewwww(1), rrrrttttmmmmoooonnnn____lllloooogggg____uuuusssseeeerrrr____ttttssssttttaaaammmmpppp(3)
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PPPPaaaaggggeeee 3333
-
-
-
-